http://publications.europa.eu/resources/authority/celex/c_5_XC_OJC

http://publications.europa.eu/resources/authority/celex/c_5_AE

http://publications.europa.eu/resources/authority/celex/c_5_IE

http://publications.europa.eu/resources/authority/celex/c_5_AG

http://publications.europa.eu/resources/authority/celex/c_5_PC_EUR

http://publications.europa.eu/resources/authority/celex/c_6_CA

http://publications.europa.eu/resources/authority/celex/c_6_CB

http://publications.europa.eu/resources/authority/celex/c_2_A_OJL

http://publications.europa.eu/resources/authority/celex/c_E_C_OJC

http://publications.europa.eu/resources/authority/celex/c_E_C_OJL

http://publications.europa.eu/resources/authority/celex/c_5_XG_OJC

http://publications.europa.eu/resources/authority/celex/c_5_M_OJC

http://publications.europa.eu/resources/authority/celex/c_3_B_OJL

http://publications.europa.eu/resources/authority/celex/c_5_AG_OJC

http://publications.europa.eu/resources/authority/celex/c_5_XX_OJC

http://publications.europa.eu/resources/authority/celex/E_G_OJC

http://publications.europa.eu/resources/authority/celex/c_4_Y_OJC

http://publications.europa.eu/resources/authority/celex/3_C

http://publications.europa.eu/resources/authority/celex/c_3_A_OJC

                            
                                <cdm:resource_legal_id_celex rdf:datatype="http://www.w3.org/2001/XMLSchema#string">32015D0046</cdm:resource_legal_id_celex>
                                
                            
                            

                            
                                <cdm:resource_legal_year rdf:datatype="http://www.w3.org/2001/XMLSchema#gYear">2014</cdm:resource_legal_year>
                                
                            
                            

                            
                                <cdm:resource_legal_number_natural_celex rdf:datatype="http://www.w3.org/2001/XMLSchema#positiveInteger">0556</cdm:resource_legal_number_natural_celex>
                                
                            
                            

                            
                                <j.0:resource_legal_id_sector rdf:datatype="http://www.w3.org/2001/XMLSchema#string">2</j.0:resource_legal_id_sector>
                                
                            
                            

                            
                                <cdm:resource_legal_type rdf:datatype="http://www.w3.org/2001/XMLSchema#string">D</cdm:resource_legal_type>
                                
                            
                            

                            
                                <cdm:resource_legal_number_corrigendum rdf:datatype="http://www.w3.org/2001/XMLSchema#positiveInteger">1</cdm:resource_legal_number_corrigendum>
                                
                            
                            

                            
                                <j.0:resource_legal_published_in_official-journal rdf:resource="http://publications.europa.eu/resource/oj/JOL_2010_276_R"/>
                                
                            
                            

                            
                                <annot:comment_on_date>{DATSIG|http://publications.europa.eu/resource/authority/fd_365/DATSIG}</annot:comment_on_date>

<annot:comment_on_date>{V|http://publications.europa.eu/resource/authority/fd_335/V} {ART|http://publications.europa.eu/resource/authority/fd_335/ART} 22</annot:comment_on_date>
                                
                            
                            

2019/06/25: Differences between ann:comment_on_date and ann:type_of_date are not fully clear

http://publications.europa.eu/resource/authority/fd_365/DATPUB

http://publications.europa.eu/resource/authority/fd_365/DATADOPT

http://publications.europa.eu/resource/authority/fd_365/DATSIG

http://publications.europa.eu/resource/authority/fd_365/DATVOT

                            
                                <annot:type_of_date>{EV|http://publications.europa.eu/resource/authority/fd_335/EV}</annot:type_of_date>
                                
                            
                            

2019/06/25: Differences between ann:comment_on_date and ann:type_of_date are not fully clear

                            
                                <cdm:resource_legal_date_vote rdf:datatype="http://www.w3.org/2001/XMLSchema#date">2009-03-25</cdm:resource_legal_date_vote>
                                
                            
                            

2015/10/14: Date of vote in sector 2 – resolutions, declarations: Joint Parliamentary Assembly of the Partnership Agreement concluded between the members of the African, Caribbean and Pacific group of States, of the one part, and the European Community and its Member States, of the other part - Resolution on racism, racial discrimination, xenophobia and related intolerance (ACP-EU 3549/03/fin) 22003P0926(14)

                            
                                <cdm:resource_legal_date_request_opinion rdf:datatype="http://www.w3.org/2001/XMLSchema#date">2013-02-19</cdm:resource_legal_date_request_opinion>
                                
                            
                            

31/10/2019: Clarify the description & methodology. How is this date treated in IMMC?

                            
                                <cdm:resource_legal_date_entry-into-force rdf:datatype="http://www.w3.org/2001/XMLSchema#date">2014-01-31</cdm:resource_legal_date_entry-into-force>
                                
                            
                            

12/03/2019: GIL-GM Provisional application of international agreements (P/12032019/4b)
The OP raised a question regarding how to proceed when the date of provisional application is earlier than the date of entry into force in the context of international agreements. The participants agreed that the date of effect should be set according to the date of provisional application so the act would be in force. Further date of effect fields (e.g. related to notification of ratification) could be added later on if necessary.

                            
                                <cdm:work_date_document rdf:datatype="http://www.w3.org/2001/XMLSchema#date">1973-03-03</cdm:work_date_document>
                                
                            
                            

COUNCIL OF THE UNION
Brussels, 30 May 2011 (01.06)
(OR. fr)
10894/11
LIMITE
JUR 272
INST 279

OPINION OF THE LEGAL SERVICE(*)

* This document contains legal advice protected under Article 4(2) of Regulation (EC)
No 1049/2001 of the European Parliament and of the Council of 30 May 2001 regarding
public access to European Parliament, Council and Commission documents, and not released
by the Council of the European Union to the public. The Council reserves all its rights in law
as regards any unauthorised publication.

Subject: Date of adoption of acts under the ordinary legislative procedure
- application of Article 13 of the Regulation on Committee Procedure (1)

1. The purpose of this opinion of the Legal Service is to clarify the determination of the date on
which acts are adopted under the ordinary legislative procedure.

2. This question has arisen in particular for acts which were adopted before the Committee
Procedure Regulation entered into force on 1 March 2011 and were signed by the Presidents
of the European Parliament and of the Council after that date. Insofar as those acts refer to the
old Decision on Committee Procedure (2), which was repealed on 1 March 2011 by the
Regulation on Committee Procedure, the question arises of the applicability of Article 13 of
the Regulation on Committee Procedure.

3. Under Article 294(4) TFEU, when the Council approves the position of the European
Parliament at first reading "the act concerned shall be adopted in the wording which
corresponds to the position of the European Parliament". The date of adoption of the act is
therefore that on which the Council approved the European Parliament's position.

4. At second reading, the act is deemed to be adopted when:
- within three months following the transmission of the first-reading position of the Council
to the European Parliament, the latter approves the Council’s position or has not taken a
decision (3); in that case, the date of adoption of the act should be considered to be that on
which the European Parliament approved the Council's position or the date when the
three-month period expired; or
- within three months following receipt of the European Parliament's amendments, the
Council approves all the European Parliament's amendments by a qualified majority (4 ); in
that case, the date of adoption of the act should be considered to be that on which the
Council approved the European Parliament's amendments.

5. At third reading, the act is adopted when, within a period of – in principle – six weeks
following the approval of a joint text by the Conciliation Committee, the European Parliament
and the Council adopt the act in question in accordance with that text(5). In that case, the date of
adoption of the act should be deemed to be the date when the act was adopted by the second
of the two institutions.

6. The signing of the act by the presidents of the two institutions, provided for in Article 297(1),
is distinct from the adoption of the act and its value consists solely in authentication of the
act (6). Therefore, even if the date of signing is included in the title of the act, as published in the
Official Journal, as the date of the act, it is not the same as the date of the act's adoption.

7. Furthermore, the Legal Service deems incorrect the practice of including the date of signing
of an act in its title, in that it can lead to confusion as to the date of the act's birth in the legal
system of the EU, despite the systematic inclusion in acts adopted by the ordinary legislative
procedure of a footnote specifying the dates on which the European Parliament and the
Council adopted their positions.

8. In conclusion, the Legal Service considers that it follows from Article 294 TFEU that the date
on which an act is adopted by the ordinary legislative procedure is the date of the decision of
the arm of the legislature that acts later (see paragraphs 3 to 5 above) and not the date of the
joint signing of the act by the presidents of the European Parliament and of the Council.
Article 13 of the Regulation on Committee Procedure therefore applies to acts adopted before
1 March 2011 but signed after that date.

(1) Regulation (EU) No 182/2011 of the European Parliament and of the Council of
16 February 2011 laying down the rules and general principles concerning mechanisms for
control by Member States of the Commission’s exercise of implementing powers (OJ L 55,
28.2.2011, p. 13).
(2) Council Decision 1999/468/EC of 28 June 1999 laying down the procedures for the exercise
of implementing powers conferred on the Commission (OJ L 184, 17.7.1999, p. 23).
(3) Article 294(7)(a) TFEU.
(4) Article 294(8)(a) TFEU.
(5) Article 294 (13) TFEU.
(6) However, as the Court of Justice has already held, failure to sign an act is an infringement of
an essential procedural requirement of the act, which may, even automatically, entail the
annulment of the act concerned by the EU's courts (Judgment of 6 April 2000 in cases
(C-287/95 and C-288/95, ECR 2000 p. I-2391, paragraph 55) Commission v. Solvay.

2015/12/22: Decisions of the European Parliament and of the Council on the mobilisation of the European Globalisation Adjustment Fund – e.g. 32015D0738
Methodology related to those documents will be completed. For the time being, Document date should contain the date from the title + comment "Date of adoption".

2017/06/30: Note from the Legal Service of the Council concerning the date of adoption of the acts adopted under the ordinary legislative procedure

                            
                                cdm:resource_legal_date_dispatch rdf:datatype="http://www.w3.org/2001/XMLSchema#date">2000-10-26</cdm:resource_legal_date_dispatch>
                                
                            
                            

31/10/2019: How is this date treated in IMMC?

                            
                                <cdm:act_preparatory_date_debate rdf:datatype="http://www.w3.org/2001/XMLSchema#date">2013-10-16</cdm:act_preparatory_date_debate>
                                
                            
                            

02/05/2015: There are currently two fields duplicating the same information – DB (date of debate) and VO (date of vote). Both were used for different notices in the past. Date of debate is usually not indicated in the OJ, there is only information concerning the session (e.g. 109th plenary session, 3—4 December 2014). Both dates should be present in DB field, but it can currently contain only one date. This should be clarified with the CELLAR.

31/10/2019: Clarification concerning differences and use cases for date of vote and date of debate. How are those dates treated in IMMC?

                            
                                <cdm:resource_legal_date_end-of-validity rdf:datatype="http://www.w3.org/2001/XMLSchema#date">9999-12-31</cdm:resource_legal_date_end-of-validity>
                                
                            
                            

Acts repealed by a subsequent act – End of validity date of repealed acts

• Acts repealed by acts which should be notified
An act is repealed by another act whose legal value depends of the date of notification.
If the notification date is not yet known, the end of validity date of the repealed act should have the following value, accompanied by the comment “repealed by” and the mention of the repealing act:

Date of document: 12/12/2013
Date of effect: 08/01/2014; Entry into force Date pub. +20 See Art 2
End of validity date: 31/12/9999 ; Repealed by 32011D0395

That date is to be modified once the notification date of the amending act is known and implemented in its notice.

• Acts declared null and void by a corrigendum
In such cases, the end of validity date is equal to the date of publication of the first act (and not to the date of the corrigendum).

Such formation must be completed by the creation of an active relation corrigendum → corrected act (for the comment to be added, see Relations).

Example 32013R1363, published in OJ L 343 of 19.12.2013 (before the corrigendum was published):
Date of document: 12/12/2013
Date of effect: 08/01/2014; Entry into force Date pub. +20 See Art 2
End of validity date: 31/12/9999

Document 32013R1363R(01) (corrigendum published in OJ L 343 of 20 December 2013) declares the publication of Commission Delegated Regulation (EU) No 1363/2013 to be considered null and void.

Document 32013R1363 (after the corrigendum 32013R1363R(01) was published):
Date of document: 12/12/2013
Date of effect: 08/01/2014; Entry into force Date pub. +20 See Art 2
End of validity date: 19/12/2013 See 32013R1363R(01)

Implicitly repealed amending acts

Basic act: Any act from sector 2, 3, 4 or 5 which has subsequently been modified.

Amending act: Any act which fully or partially modifies the basic act to which it relates. An amending act can be composed either of provisions which only relate to one basic act ("not-autonomous provisions") or of provisions which relate to more than one or to none basic act, and which produce a legal effect of their own (“autonomous provisions”).

An amending act is deemed implicitly repealed when the basic act to which it relates is repealed and does not explicitly mention that its successive amendments are also repealed, as long as the amending does not contain any autonomous provisions.

The end of validity date of the amending act should be the same as the one of the repealed basic act.

The information must be completed by the creation of an active relation act repealing the basic act → amending act (for implicitly repeals, see Relations).

See also comment (21/9/2015) Implicitly repealed amending acts – information form the Legal Service

Anti-dumping measures

A definitive anti-dumping measure shall expire five years from its imposition or five years from the date of conclusion of the most recent review (Council regulation (EC) No 1225/2009, art. 11.2).

There are two basic scenarios for the amendments concerning the end of validity date of an implementing measure:

Scenario 1

Publication of: Basic implementing regulation imposing a definitive anti-dumping duty
Date of application = 01-01-2014
End of validity date = 31-12-2018

Publication of: Implementing regulation amending the basic regulation (not repealing or amending the validity)
Date of application = DD-MM-YYYY
End of validity date = 31-12-2018

Publication of: Notice of the impending expiry of certain anti-dumping measures
(Published in OJ before the expiry of the basic regulation.)
No change needed for the end of validity of the basic implementing regulation or the amending regulation.

Scenario 2 (the dates in EV date are to be used successively, following the sequence of events described below)

Publication of: Basic implementing regulation imposing a definitive anti-dumping duty
Date of application = 01-01-2014
End of validity date = 31-12-2018

Publication of: Implementing regulation amending the basic regulation (repealing or amending the validity, in this case to 31-12-2019)
Date of application = DD-MM-YYYY
End of validity date = 31-12-2019 + change of the end of validity date of the basic implementing regulation to be done

Publication of: Notice of initiation of partial interim review of the anti-dumping measures
The basic implementing regulation should remain in force pending of the outcome of the review:
The end of validity date of the basic and amending implementing regulations has to be changed, until the review is published (should be changed to 31-12-9999)

Publication of: New basic implementing regulation imposing a definitive anti-dumping duty
Date of application = 01-04-2020
End of validity date = 31-03-2025
The end of validity date of the basic (A) and amending implementing (B) regulations has to be changed to the definitive date (31-03-2020 – date of application of the new basic regulation minus one day).

2015/09/21: Implicitly repealed amending acts – information form the Legal Service
When a legal act is repealed, it is repealed with all subsequent amendments, even when they are not listed in the repealing act, unless for specific reasons it is expressly provided that certain amending acts are not repealed together with the main act.

2015/09/23: Recommendations from sector 3
Generally, recommendations from sector 3 should not have the end of validity.
It should be created only if there is another document repealing some of the previous recommendations (e.g. 32014H0897). NB: Currently there are 1058 recommendations in sector 3 containing EV date (DTS_SUBDOM = LEGISLATION AND FM = "RECOMM" NOT EV=NULL). Correction to be done.

15/12/2016: End of validity of repealed acts
Manual of precedents for acts established within the Council of the EU, 2002:

3. REPEAL

The repeal of an act or of certain of its provisions means that it/they cease( s) to be in force, either because the arrangements that it/they introduced expire or are replaced by other arrangements, or because the whole act, including all its successive amendments is replaced by a codified/recasted act (*).

Regulation ...... [and Regulation ...... taken in implementation thereof] shall be repealed. 1

Article 3 of Regulation ...... shall be repealed.

NB: In these two cases it is understood that the repeal takes effect on the date of entry into force or, where appropriate, the date of application of the repealing act.

Regulation ...... shall be repealed with effect from ...... [date on which the repealing

Regulation is brought into effect].

NB: In that case, the repeal shall take effect on a date which differs from that of the entry into force of the repealing act.

(*) "Consolidating act" from the original version was replaced by "a codified/recasted act.

28/02/2017: Ephemeral acts, fisheries - prohibition of fishing
Change of the methodology for ephemeral acts – EV not to be created.
Documents related to prohibition of fishing – there should be a real EV date inserted, based on the text.

29/06/2017: Information from SJ concerning validity of delegated/implementing acts
A delegated/implementing/comitology act does not automatically get repealed on the repeal of the basic legislative act on the basis of which it got adopted. An act is valid if its legal basis was valid at the time of adoption of the act. Such a delegated/implementing/comitology act would need to be specifically repealed by the Commission

15/03/2019: Association agreements – new Member States
Notices covering the associationagreements with new MS contain value 31/12/9999 in EV date. Therefore, the in force indicator says "In force".
We assume the EV date should be equal to the date of accession (minus 1 day); but this assumption has not been confirmed by any relevant authority.
Based on this, it was decided to remove EV field from such notices.
See https://webgate.ec.europa.eu/publications/jira/browse/LAAION-540
Examples: 22005A0617(02), 22005A0617(01), 22003A0515(01), 21993A1231(18), 21993A1231(15)
29/09/2016: GIL-GM Amended proposal – end of validity date of the initial proposal
Commission proposal can be amended a couple of times and that such amended proposals are published as separate notices on EUR-Lex. The questions is whether the end of validity date of the initial proposal can be understood as being the date of the adoption of the 1st amended proposal (minus 1 day) and whether the end of validity date of the 1st amended proposal can be understood as being the date of the adoption of the second amended proposal (minus 1 day)? Or should the first and second amended proposals be understood only as texts amending the initial proposal but not replacing it? The amended proposals can contain only the amendments or the amendments plus the original proposal, depending on the case-by-case basis.
The participants agreed that both the initial proposal and the amended proposal(s) should keep having the fictional date of end of validity (implying that they are "pending"), until a final act is adopted. After this, the date of adoption of the final act becomes the date of end of validity of both the initial proposal and amended proposals.

12/03/2019: GIL-GM Follow-up of Court's decisions on annulment (P/12032019/4a)
The legal analysis methodology does not follow up on the annulments of legal acts by judgments of the Court of Justice. Currently the date of end of validity of those acts remains indefinite; therefore, they remain marked as 'in force'.
The Commission Legal Service was consulted and considered that the effect should be as if it had never existed, therefore the value contained in the date of effect field should be reproduced in the date of end of validity, and the in force indicator switched to 'not in force'. The participants agreed on this solution and indicated that the comment 'declared void by' should be shown below the title, next to the in force indicator coloured point.
This solution should also be applied to cases where the judgment annuls the decision but orders to maintain the effects of the decision in force.

Example https://eur-lex.europa.eu/legal-content/EN/ALL/?qid=1571896291605&uri=CELEX:62011CJ0658:

On those grounds, the Court (Grand Chamber) hereby

1. Annuls Council Decision 2011/640/CFSP of 12 July 2011 on the signing and conclusion of the Agreement between the European Union and the Republic of Mauritius on the conditions of transfer of suspected pirates and associated seized property from the European Union-led naval force to the Republic of Mauritius and on the conditions of suspected pirates after transfer;

2. Orders that the effects of Decision 2011/640 be maintained in force

12/03/2019: GIL-GM End of validity of international agreements when the decision on the signing was declared void by CdJ (P/12032019/4b)
The OP raised the question on how to proceed when the Court annuls the decision on the signing of an agreement. The participants agreed that in both decision and agreement cases the value corresponding to the date of entry into force should be set in the date of end of validity field.
See for example https://eur-lex.europa.eu/legal-content/EN/ALL/?qid=1571896291605&uri=CELEX:22011A0930(01)

                            
                                <cdm:resource_legal_date_deadline rdf:datatype="http://www.w3.org/2001/XMLSchema#date">2014-12-31</cdm:resource_legal_date_deadline>
                                
                            
                            

                            
                                <cdm:resource_legal_date_signature rdf:datatype="http://www.w3.org/2001/XMLSchema#date">2014-03-25</cdm:resource_legal_date_signature>
                                
                            
                            

31/10/2019: Check if this date shall be also available in legislative acts & budget

                            
                                <cdm:legislation_secondary_date_notification rdf:datatype="http://www.w3.org/2001/XMLSchema#date">2014-01-31</cdm:legislation_secondary_date_notification>
                                
                            
                            

14/10/2015: Methodology
related to the Council decisions or directives which specify to whom they are addressed and indicating the date of effect was updated (Analytical methodology, point 2).

2017/10/16: EFTA Surveillance Authority Decision having addressees: Date of document (=date of adoption) = the date of notification (and therefore date of effect)

From: Mathisen, Gjermund [mailto:Gjermund.Mathisen@eftasurv.int]
Sent: jeudi 12 octobre 2017 11:16
To: BRKIC Dejan (OP)
Cc: Jordal, Christian; OP LEGAL ANALYSIS
Subject: RE: EFTA decisions - date of notification

Dear Mr Brkic,

We will attempt to add that to our routines, yes. (I note, to be more precise, that I would not expect this to happen every year; it’s more exceptional than that.)

Kind regards,

Gjermund Mathisen
Director of Competition and State Aid

Rue Belliard 35, 1040 Brussels

Phone: +32 2 286 18 60 (direct line)
Phone: +32 2 286 18 21 (assistant)
E-mail: Gjermund.Mathisen@eftasurv.int
www.eftasurv.int

From: BRKIC Dejan (OP) [mailto:Dejan.BRKIC@publications.europa.eu]
Sent: 12 October 2017 11:04 AM
To: Mathisen, Gjermund <Gjermund.Mathisen@eftasurv.int>
Cc: Jordal, Christian <Christian.Jordal@eftasurv.int>; OP LEGAL ANALYSIS <OP-LEGAL-ANALYSIS@publications.europa.eu>
Subject: RE: EFTA decisions - date of notification

Dear Ms Mathisen,

Thanks a lot for this confirmation.
It would be good if you could also inform us about those exceptional cases where the date of adoption is not the date of notification. You can do so by sending an e-mail to our functional mailbox
OP-LEGAL-ANALYSIS@publications.europa.eu

Kind regards,

Dejan BRKIC
Legal Analysis and Documentary Management
_________________
Publications Office of the European Union
Dissemination and Reuse Directorate
Documentary Management and Metadata Unit

2985 Luxembourg • LUXEMBOURG
Tel: +352 2929 42217
Dejan.BRKIC@publications.europa.eu
http://publications.europa.eu


From: Mathisen, Gjermund [mailto:Gjermund.Mathisen@eftasurv.int]
Sent: jeudi 12 octobre 2017 10:10
To: BRKIC Dejan (OP)
Cc: Jordal, Christian
Subject: RE: EFTA decisions - date of notification

Dear Mr Brkic,

I have had your email below forwarded from the EFTA Secretariat. My apologies for getting back to you so late.

Indeed, you may assume that any decisions in the field of State Aid or Competition, which are addressed to a specific addressee, be that a State or (a) private party/ies, apply as from the date of adoption. As a rule, we always notify such decisions to the addressee(s) on the date of adoption. If, exceptionally, we should fail to do so, we will notify the EFTA Secretariat of the notification date.

I hope this answers your question.

Kind regards,

Gjermund Mathisen
Director of Competition and State Aid

20/02/2019: If the real date of notification is not known, the date of publication + annotation The act was notified but the date of notification is not available on EUR-Lex – the date of publication is used instead
<COMMENT_ON_DATE>{titleAndReference.draft.disclaimer.new|http://publications.europa.eu/resource/authority/fd_365/titleAndReference.draft.disclaimer.new}</COMMENT_ON_DATE>
Additionally, if the date of effect depends on the date of notification, the date of publication shall be also used in IF field.
Example: https://eur-lex.europa.eu/legal-content/EN/ALL/?qid=1550651686388&uri=CELEX:32015D0248

                            
                                <cdm:question_parliamentary_date_reply rdf:datatype="http://www.w3.org/2001/XMLSchema#date">2013-02-18</cdm:question_parliamentary_date_reply>
                                
                            
                            

                            
                                <cdm:directive_date_transposition rdf:datatype="http://www.w3.org/2001/XMLSchema#date">2014-09-30</cdm:directive_date_transposition>
                                
                            
                            

31/10/2019: List of relevant subproperties:
cdm:directive_date_transposition
cdm:decision_date_transposition
cdm:recommendation_date_transposition
cdm:recommendation_ecsc_date_transposition
cdm:regulation_date_transposition
cdm:cooperation_police-and-judicial_date_transposition

31/10/2019: To be checked which properties are used + remove those that are not needed

                            
                                <cdm:resource_legal_is_about_concept_directory-code rdf:resource="http://publications.europa.eu/resource/authority/fd_555/1530"/>
                                
                            
                            

In order to maintain consistency, some rules must be respected by the indexation:

For modifying documents, the same descriptors should be used as for the modified document.

For documents related to the anti-dumping – 11.60.40.20 Anti-dumping measures should be always used.

For legislation adopted on a legislative proposal, use the descriptors from the proposal.

For agreements adopted by decision of the Council, use the same descriptors as in the act adopting the agreement.

For documents concerning the budget use 01.60.20 Budget.

Correspondance between TEU & TFEU and directory concepts

Treaty on European Union

Articles 1-8: 01.10 Principles, objectives and tasks of the Treaties
Articles 9-12: 01.10 Principles, objectives and tasks of the Treaties / 20.20 European citizenship
Articles 13-19: 01.40.00.00 General, financial and institutional matters / Provisions governing the institutions
Article 20: No specific heading for administrative cooperation. GO TO: the different domains where the cooperation takes place i.e. taxation, judicial cooperation, patents, civil law, etc.
Articles 21-22: 11 External relations
Articles 23-46: 18 Common Foreign and Security Policy
Articles 47-55: 01.10 Principles, objectives and tasks of the Treaties / 01.30 Scope of the Treaties

Treaty on the functioning of the European Union

Articles 1-6: 01.10 Principles, objectives and tasks of the Treaties
Articles 7-17: 01.10 Principles, objectives and tasks of the Treaties
Articles 18-25: 20.20 European citizenship
Articles 26-27: 13.30 Internal market: approximation of laws / 13.40 Internal market: policy relating to undertakings
Articles 28-32: 02 Customs Union and free movement of goods
Article 33: 19.30.30 Customs cooperation
Articles 34-37: 08.90.00.00 Competition policy / National trading monopolies
Articles 38-44: 03 Agriculture / 04 Fisheries
Articles 45-48: 05.10 Freedom of movement for workers
Articles 49-62: 06 Right of establishment and freedom to provide services
Articles 63-66: 10.40 Free movement of capital
Articles 67-76: 19 Area of freedom, security and justice
Articles 77-80: 19.10.10 Elimination of internal border controls / 19.10.20 Crossing external borders / 19.10.30 Asylum policy / 19.10.40 Immigration and the right of nationals of third countries
Article 81: 19.20 Judicial cooperation in civil matters
Articles 82-86: 19.30.20 Judicial cooperation in criminal matters
Articles 87-89: 19.30.10 Police cooperation
Articles 90-100: 07 Transport policy
Articles 101-106: 08 Competition policy
Articles 107-109: 08.60 State aids and other subsidies
Articles 110-113: 08 Competition policy
Articles 114-118: 08 Competition policy / 17.20 Intellectual property law
Article 119: 10.20 Monetary policy / 10.30 Economic policy
Articles 120-126: 10.30 Economic policy
Articles 127-133: 10.20 Monetary policy
Articles 134-135: 10.20.10 Institutional monetary provisions / 10.30.10 Institutional economic provisions
Articles 136-138: 10.30.30 Economic and monetary union
Articles 139-144: 10.30.30 Economic and monetary union
Articles 145-150: 05.20.30 Employment and unemployment
Articles 151-161: 05.20 Social policy
Articles 162-164: 05.20.10 European Social Fund (ESF)
Articles 165-166: 15.30 Health protection / 16.30 Education and training (No specific domain for Sport in the Directory Codes)
Article 167: 16.40 Culture
Article 168: 03 Agriculture (03.50.20 Plant health; 03.50.30 Animal health and zootechnics) / 15.30 Health protection
Article 169: 15.20 Consumers
Articles 170-172: 13.60 Trans-European networks
Article 173: 13.10 Industrial policy: general, programmes, statistics and research / 13.20 Industrial policy: sectoral operations
Articles 174-178: 14 Regional policy and coordination of structural instruments
Articles 179-190: 13.10.30 Research and technological development / 16.10 Science (No specific domain for Space in the Directory Codes)
Articles 191-193: 15.10 Environment
Article 194: 12 Energy
Article 195: 06.20.20.50 Right of establishment and freedom to provide services / Sectoral application / Service activities / Leisure services // 13.20.70.00 Industrial policy and internal market / Industrial policy: sectoral operations / Other industrial sectors (No specific domain for Tourism in the Directory Codes)
Article 196: 15.20.30.00 Environment, consumers and health protection / Consumers / Protection of health and safety
Article 197: No specific heading for administrative cooperation. GO TO: the different domains where the cooperation takes place i.e. taxation, internal market, external relations, etc.
Articles 198-204: 11.70.40.10 External relations / Development policy / Associations / Overseas countries and territories (PTOM)
Article 205: 11.50 External relations / Action in favour of countries in transition // 11.70.20.00 External relations / Development policy / Aid to developing countries
Articles 206-207: 11.60.10.00 External relations / Commercial policy
Articles 208-214: 11 External relations
Article 215: 18 Common Foreign and Security Policy
Articles 216-219: 11 External relations
Articles 220-221: 11.30.40.00 External relations / Multilateral relations / Cooperation with international and non-governmental organisations
Article 222: 14.40.20.00 Regional policy and coordination of structural instruments / Autonomous regional action / Aid for stricken regions
Articles 223-234: 01.40.20 Parliament
Articles 235-236: 01.40.00.00 General, financial and institutional matters / Provisions governing the institutions (No specific heading in the Directory Codes)
Articles 237-243: 01.40.30 Council
Articles 244-250: 01.40.40 Commission
Articles 251-281: 01.40.50 Court of Justice
Articles 282-284: 01.40.75 European Central Bank
Articles 285-287: 01.40.60 Court of Auditors
Articles 288-299: 01.40.10.00 General, financial and institutional matters / Provisions governing the institutions / General
Article 300: 01.40.65 Committee of the Regions / 01.40.70 Economic and Social Committee
Articles 301-304: 01.40.70 Economic and Social Committee
Articles 305-307: 01.40.65 Committee of the Regions
Articles 308-309: 01.40.80 European Investment Bank
Article 310: 01.60.00.00 General, financial and institutional matters / Financial and budgetary provisions
Article 311: 01.60.30 Own resources
Articles 312-319: 01.60.20.00 General, financial and institutional matters / Financial and budgetary provisions / Budget
Articles 320-324: 01.60.00.00 General, financial and institutional matters / Financial and budgetary provisions
Article 325: 01.60.00.00 General, financial and institutional matters / Financial and budgetary provisions / 09.50.00.00 Taxation / Prevention of tax evasion and avoidance
Articles 326-334: No specific heading for administrative cooperation. GO TO: the different domains where the cooperation takes place i.e. taxation, judicial cooperation, patents, civil law, etc.
Articles 335-358: 01.10 Principles, objectives and tasks of the Treaties / 01.20 General provisions / 01.30 Scope of the Treaties / 01.40 Provisions governing the institutions

dir-eu-legal-act:0120

dir-eu-legal-act:0860

dir-eu-legal-act:0860
dir-eu-legal-act:11401010

dir-eu-legal-act:11401010

dir-eu-legal-act:0810
dir-eu-legal-act:11401010

dir-eu-legal-act:11401010
dir-eu-legal-act:074020

dir-eu-legal-act:11603030
dir-eu-legal-act:18

dir-eu-legal-act:0840

dir-eu-legal-act:016020

dir-eu-legal-act:0205

dir-eu-legal-act:103020

dir-eu-legal-act:15102010

dir-eu-legal-act:133015

                            
                                <cdm:work_is_about_concept_eurovoc rdf:resource="http://eurovoc.europa.eu/3526"/>
                                
                            
                            

PART II: Applying the general indexing principles: concrete rules and examples from the already indexed EUR-Lex documentary collection

1. Use EuroVoc for indexation and the Directory code and Subject headings for classification

While indexing with EuroVoc, indexer should keep in mind the different purpose and the use of an indexing tool and a classification tool.
The systematic use of general EuroVoc terms (most frequently top terms) can easily result in classifying the documents instead of indexing them, so their use should be limited to documents at very general level and only to documents that really speak about the selected general descriptor.
This principle is in line with the principle that the most specific EuroVoc term should be used. Before assigning a general term (top term) to a document, indexer is asked to examine whether one of its specific term corresponds better to the content of the document.
Classifying instead of indexing may occur not only at top terms level but at specific level as well. To avoid this, indexer is always asked to verify before assigning a descriptor to a document whether the chosen descriptor really corresponds to the content of the document (indexation) or only classifies the document by referring to its main subject(s) (classification).

i) 32011D0302: Council implementing decision 2011/302/CFSP concerning restrictive measures against Syria
This document concerns in general the common foreign and security policy. In this case the descriptor CFSP was used to classify the document (see classification under the Directory code and Subject mater):

EUROVOC descriptor:
international sanctions / human rights / CFSP / restriction of liberty

Directory code:
18.00.00.00 Common Foreign and Security Policy

Subject matter:
Common foreign and security policy

ii) 32011D0019(01): Decision of the European Central Bank of 15 November 2011 amending Decision ECB/2007/7 concerning the terms and conditions of TARGET2-ECB (ECB/2011/19)
This document concerns in general the European Monetary Union. In this case the descriptor Economic and Monetary Union was used to classify the document (see classification under the Directory code and Subject mater):

EUROVOC descriptor:
Economic and Monetary Union / electronic banking / intra-Community payment

Directory code:
10.30.30.00 Economic and monetary policy and free movement of capital / Economic policy / Economic and monetary union

Subject matter:
Economic and Monetary Union, European Central Bank, Euro

2. Follow the three stages of indexing

If the three intellectual stages of the indexation process are not respected, it may lead to some typical indexation errors and may negatively affect the performance of the query.
These errors are the followings:

A. Missing descriptors
If descriptors are missing, the query system will not retrieve the relevant documents answering to the users' query. There will be an information loss or 'silence' and desscriptor has to be added.

Missing descriptors occurs due to imperfection:
• either in identification of the essential concepts with a potential value for the users during document analysis
• or in translation of these identified concepts into EuroVoc descriptors

If there is no descriptor in EuroVoc corresponding to the selected concept (neither at the same level of specificity, nor at the next higher level), indexer should try to represent the given concept by the combination of several existing descriptors.
If it is not possible, propositions can be sent to the OP by using the 'Contribute' menu of the EuroVoc website in order to include a new descriptor in EuroVoc.

i) 2011CN0414: Reference for a preliminary ruling from the Polimeles Protodikio Athinon (Greece) lodged on 8 August 2011
This document concerns questions, which should be clarified by the Court of Justice: "Under Article 27 of the TRIPS Agreement are chemical and pharmaceutical products patentable subject matter provided that they satisfy the requirements for the grant of patents and, if so, what is the scope of their protection?"

Descriptor TRIPS – the main descriptors which should be used to cover the subject of the document – was missing:

EUROVOC descriptor:
European patent / patent law / chemical product / pharmaceutical product

ii) 32011R1004: Commission Implementing Regulation (EU) No 1004/2011 of 11 October 2011 amending the representative prices and additional import duties for certain products in the sugar sector fixed by Implementing Regulation (EU) No 971/2011 for the 2011/12 marketing year
One of the main descriptors ("representative price") was missing:

EUROVOC descriptor:
Community import / raw sugar / CCT duties / beet sugar / cane sugar

iii) 32011D0634: Council Decision of 17 May 2011 on the signing, on behalf of the European Union, and provisional application of the International Cocoa Agreement 2010
• One of the main descriptors ("signature of an agreement") was missing.
• If a document concerns an agreement, also the type and the field (EC trade agreement) of the agreement should be expressed by indexing terms – see also Annex III (Descriptors clarification), EC agreement.

EUROVOC descriptor:
sustainable development(*) / economic growth(*) / cocoa
(*) In this case too general descriptors were used. See point 2.3 (Be as specific as possible).

B. Incorrect descriptors
If descriptors are incorrectly used (not relevant, out of context), the query system will retrieve several but irrelevant documents, there will be a 'noise' In that case, incorrect descriptors have to be deleted.

The use of incorrect descriptors is due to:
• either the misunderstanding of the content of the document
• or to the defect in examining the contextual and semantic environment of the selected descriptor (non-preferred terms, related terms, hierarchy, notes) which may lead to the misunderstanding of the selected descriptor

Theoretically, the semantic environment of a descriptor helps to clarify the meaning of a descriptor, but if it is not the case, clarification and additional notes to a EuroVoc term can be demanded from the OP.

i) 620091TA00118: Case T-118/09: Judgment of the General Court of 5 October 2011 — La Sonrisa de Carmen and Bloom Clothes v OHIM — Heldmann (BLOOMCLOTHES)

EUROVOC descriptor:
real estate business / European trademark / registered trademark

This document concerns the trademark law. The subject of commercial activity of the companies – parties to the action – is not specified in the text. Anyway, the name of the trademark in question (Blomclothes) could indicate the field of the business activity – clothing. For more information a more detailed searching is needed in this case (related documents, web sites of the companies etc.).

ii) 52011XC1011(04): Commission communication pursuant to Article 17(5) of Regulation (EC) No 1008/2008 of the European Parliament and of the Council on common rules for the operation of air services in the Community

EUROVOC descriptor:
public servi / invitatice / invitation to tender / inland transport / air transport /Greece

This document concerns an invitation to tender for providing service of general interest (air transport). The descriptor "public services" refers to "the body providing a service" (see SN). Descriptor "services of general interest" should be used in this case.

iii) 52011DC0666: Communication from the Commission to the European parliament and the Council: Enlargement Strategy and Main Challenges 2011-2012

EUROVOC descriptor:
Albania / Community acquis / Turkey / ISPA / accession criteria / Macedonia

Macedonia is a region of Greece. This communication concerns the "Former Yugoslav Republic of Macedonia".

3. Be as specific as possible

According to the general indexing principle, the most specific EuroVoc term should be selected.
If a document is indexed at a higher/more general level than the level of specificity of the selected concept, it will generate ‘noises’ and user will get irrelevant results.

i) 32011D0739: Council Decision of 20 October 2011 on the conclusion of the Agreement between the European Union, the Swiss Confederation and the Principality of Liechtenstein amending the Additional Agreement between the European Community, the Swiss Confederation and the Principality of Liechtenstein extending to the Principality of Liechtenstein the Agreement between the European Community and the Swiss Confederation on trade in agricultural products

EUROVOC descriptor:
Liechtenstein / foodstuff / EC agreement / designation of origin / Switzerland / agricultural product / ratification of an agreement

The more specific descriptor "EC trade agreement" should be used in this case. "EC agreement" and "EC trade agreement" belongs to the same hierarchical line. "EC trade agreement is the NT of 'EC agreement".

ii) 62006FB0105: Case F-105/06: Order of the Civil Service Tribunal (First Chamber) of 27 September 2011 — Lübking and Others v Commission
The case concerns: "Annulment of the Commission’s decision published in Administrative Notices No 85 2005 of 23 November 2005 in so far as it provided for promotion of the applicants to grade A*9 and not grade A*10 in the 2005 promotion exercise."

EUROVOC descriptor:
equal treatment / appointment of staff / professional career / staff assessment / European official

The more specific descriptor "promotion" should be used in this case. "Professional career" and "promotion" belong to the same hierarchical line. "Promotion" is the NT of "Professional career".

iii)32011R1136: Commission Implementing Regulation (EU) No 1136/2011 of 9 November 2011 establishing the standard import values for determining the entry price of certain fruit and vegetables

EUROVOC descriptor:
fruit / Community import / vegetable / import price / common organisation of markets

Ephemeral documents usually contain (in their annexes) the concrete product names or the Combined Nomenclature (CN) codes of the products concerned by the act. Indexer is asked to use the most specific descriptor corresponding to the products and not only descriptors referring to the category of the concerned products. More specific descriptors (citrus fruit, grape, pip fruit and fruit vegetable) should be used in this case.

If EuroVoc has no descriptor at the same level of specificity as the selected concept, the descriptor at the next higher level should be chosen: Commission Implementing Regulation (EU) No 388/2011 of 19 April 2011 concerning the authorisation of maduramicin ammonium alpha as a feed additive for chickens for fattening (holder of authorisation Alpharma (Belgium) BVBA) and amending Regulation (EC) No 2430/1999 Text with EEA relevance: Since EuroVoc has no descriptor for ‘maduramicin ammonium’ (which is an antibiotic), use the descriptor at the next higher level.

In some cases, specific terms are considered in EuroVoc as non-preferred terms of generic terms. (e.g. name of classes and their components – reptile NPT crocodile)

4. Simultaneous use of several descriptors belonging to the same hierarchical line

Before indexers select a Eurovoc term, they should navigate the content of the thesaurus and analyze the hierarchical relationships of the selected terms. It will alert them to the existence of a more or a less generic term belonging to the same hierarchical line: if both of them suits to the content of the document, the most specific one should be used.

i) 32011R0418: Commission Implementing Regulation (EU) No 418/2011 of 28 April 2011 amending the representative prices and additional import duties for certain products in the sugar sector fixed by Regulation (EU) No 867/2010 for the 2010/11 marketing year

EUROVOC descriptor:
sugar product / syrup / representative price / CCT duties
Descriptors sugar product and syrup belong to the same hierarchical line. The most specific should be chosen.

ii) 62011CN0454: Reference for a preliminary ruling from the Latvijas Republikas Augstākās tiesas Senāta Adminsitratīvo (Republic of Latvia) lodged on 1 September 2011 — Gunārs Pusts v Lauku atbalsta dienests

EUROVOC descriptor:
aid recipient / terms of aid / aid system
Descriptors aid recipient and aid system belong to the same hierarchical line. The most specific should be chosen.

5. Prefer pre-coordinated descriptors to ‘simple’ descriptors or to the combination of two or more ‘simple’ descriptors

EuroVoc, originally built up specifically for processing the documentary collection of the EU institutions, contains a large number of pre-coordinated descriptors in the field of EU activities. These pre-coordinated descriptors (e.g. ‘import (EU)’) exist in parallel with ‘simple’ descriptors (e.g. ‘import’), either with a hierarchical relationship between them (same hierarchical line) or as related terms, belonging to different top terms or microthesauri.
Giving preference to the use of pre-coordinated EuroVoc descriptors is essential since it affects the performance of the query results.
In EUR-Lex, there are an important number of documents that requires pre-coordinated descriptors. If EuroVoc does not contain the necessary pre-coordinated descriptor, propositions can be sent to the OP via the Contribute menu of Euro.

Examples of pre-coordinated descriptors:
appointment of staff (in general, BT personnel administration). Do not use this descriptors for indexing a document about the appointments in EU institutions/bodies Ex: 32011D0243
appointment of members – pre-coordinated – use only for the appointments in EU institutions, bodies, agencies

budget financing – resources of a budget (national budget, budget of an organisation, etc.)
financing of the EU budget – pre-coordinated – concerns the different types of resources of the EU (Where does the money come from? How is EU budget is financed?)

import Ex: 32011R0385
import (EU) pre-coordinated

export Ex: 52011PC0245
export (EU) pre-coordinated

bilateral agreement – See SN – use for documents about agreement between two States Ex: 52011SC0640
EC agreement – pre-coordinated – use for documents about agreement between the EU in one part + third country or (international) organisation in combination with the country name or the organisation's name. If possible, use specific pre-coordinated descriptors for the different types of EU agreements (European association agreement, association agreement (EU), cooperation agreement (EU), interim agreement (EU), trade agreement (EU), negotiation of an agreement (EU)) EX: 32011D0334

action programme – BT management (UF framework programme, plan of action, work programme) Do not use for EU programmes Ex: 52011AE0533
EU programme – pre-coordinated

6. Use geographical descriptors

Domain 72 Geograpy of EuroVoc contains geographical descriptors. Use descriptors of countries when a document concerns specifically one or more countries or examines a particular situation in a given country. For example:
• agreement with a country
• action against a State / judgment of a court concerning a country
• national statistics
• state aid regime of a country / authorization of State aid, etc.
• EU financing expenditure in a State
• origin of a product
• national law of a State

Group of countries / international organisations
If the document speaks about group of countries or international organisations as a whole, do not list the name of the member countries, but use only the descriptor concerning the group from the domain 76 International organisations.
However, if needed, country names and descriptors referring to an organisation/group of country can be used simultaneously since they do not belong to the same hierarchical line and domain.

52010XG0415(01): Notice for the attention of the persons, entities and bodies to which restrictive measures provided for in Council Decision 2011/239/CFSP apply

EUROVOC descriptor:
international sanctions / economic sanctions / natural person
A geographical descriptor is missing (Myanmar). Restrictive measures are provided against Burma/Myanmar.

Regions
Only the names of regions of EU Member States are in EuroVoc, but not those of third countries.
Use regions' names when a document is specifically about a region of an EU Member State.
If needed, regions names can be used together with country names since they do not belong to the same hierarchical line.

52010X0416(03): Summary information communicated by Member States on State aid granted

EUROVOC descriptor:
Italy / fishing industry / aid system / control of State aid / small and medium-sized enterprises / aquaculture / State aid
A geographical descriptor is missing (Sardegne). State aid was granted by the 'Regione Autonoma della Sardegna'.

7. Physical entity of the document

Indexation of the EUR-Lex documentary collection with EuroVoc should not concern the type and/or the author of the document. This information are covered by other metadata, EuroVoc descriptors should be only used to index the content of the document.

Author
The use of ‘institutions’ descriptors (EU institutions, bodies, services, organisations, agencies and international organizations) should be limited to documents which are about:
• the functioning of an institution (rules of procedures, composition, appointment, etc.)
• the competencies of an institution
• the role of an institution
• the activity of an institution
• agreements, cooperation between institutions

Do not use ‘institutions’ descriptors of EuroVoc when the given institution or body is the author of the document and the document does not speak about its functioning, activity, etc.

52011SC0622): Commission staff working paper accompanying the report from the Commission to the European parliament and the Council

EUROVOC descriptor:
Community financing / EC Commission / information

Author:
European Commission

Descriptor EC Commission refers to the author of the document. This descriptor should be deleted.

Type of document/of act
EuroVoc descriptors belonging to the top term ‘document’ or to ‘EU act’ should not be used for identifying the type of document. Other field of metadata is available for that purpose.

52010XX1016(01): Opinion of the European Data Protection Supervisor on Promoting Trust in the Information Society by Fostering Data Protection and Privacy

EUROVOC descriptor:
data processing / personal data / Community opinion / European data protection supervisor

Form:
Opinion

Descriptor Community opinion refers to the type of the document. This descriptor should be deleted.

Type of procedure/parties (case-law)
Descriptors referring to the nature of the proceeding, to the parties of proceeding (applicant, defendant) etc. should not be used. This information is covered by other metadata (PR).

62008TA0449: Case T-449/08: Judgment of the General Court of 18 October 2011 — SLV Elektronik v OHIM — Jiménez Muñoz (LINE)

EUROVOC descriptor:
European trademark / trademark law / action for annulment of an EC decision / lighting equipment

Type of procedure:
Action for annulment - successful

Descriptor action for annulment of an EC decision refers to the type of the procedure. This descriptor should be deleted.

8. Achieve indexing consistency

Concerning the EUR-Lex documentary collection, the creation of flexible templates can be good solutions for achieving indexing consistency. The indexing terms in these templates may change according to the content of the document.
Already defined templates are listed in the third part of the document.

eurovoc:1474

eurovoc:2809

eurovoc:5541
eurovoc:889

eurovoc:3581

eurovoc:5267

eurovoc:4505
eurovoc:3160
eurovoc:6369

eurovoc:7
eurovoc:5542

eurovoc:183
eurovoc:69

eurovoc:5158
eurovoc:6013
eurovoc:933

eurovoc:187
eurovoc:5618
eurovoc:3813
eurovoc:5451
eurovoc:1631

eurovoc:368
eurovoc:6212
eurovoc:843

eurovoc:4042
eurovoc:2539
eurovoc:347

eurovoc:1474
eurovoc:2850

eurovoc:2081
eurovoc:5451

                            
                                <cdm:resource_legal_is_about_subject-matter rdf:resource="http://publications.europa.eu/resource/authority/fd_070/UD"/>
                                
                            
                            

subject-matter:EXT

subject-matter:DGEN

subject-matter:AIDE

subject-matter:AIDE
subject-matter:AELE

subject-matter:AELE

subject-matter:CONC
subject-matter:AELE

subject-matter:
subject-matter:AELE

subject-matter:TRAN

subject-matter:PESC

subject-matter:MERG
subject-matter:CONC

subject-matter:BUDG

subject-matter:LCM
subject-matter:AELE

subject-matter:UEM
subject-matter:PECO

subject-matter:NUCL

subject-matter:SANT

                            
                                <cdm:case-law_is_about_concept_new_case-law rdf:resource="http://publications.europa.eu/resource/authority/fd_578/3.02.00"/>
                                
                            
                            

                            
                                <cdm:work_created_by_agent rdf:resource="http://publications.europa.eu/resource/authority/corporate-body/EP"/>
                                
                            
                            

If there are no concepts available for different association/cooperation councils or joint committees in the relevant NAL corporate-body (as for example EU – Republic of Moldova Association Council), please use a combination of more generic concepts (Association Council – COUN_ASS, Cooperation Council – COUN_COOP, Joint Committee – CMT_CONJOIN etc.) together with the country name (codes coming from corporate-body + country).

April 2015: For parliamentary questions, the author field contained also the name of the Member of the European Parliament in the past. However, because of missing mapping in the CELLAR, those names are currently not displayed on the new EUR-Lex. Possible solutions should be analysed.

<rdf:Description rdf:nodeID="A2">
<rdf:type rdf:resource="http://www.w3.org/2002/07/owl#Axiom"/>
<annot:build_info>cdm:CDM_2.1.7 tdm:1523 xslt:3945 saxon:9.0.0.1J JVM:1.6.0_29 metaconvJar:1.1.9 builddate:06/12/2013 15:38:22</annot:build_info>
<annot:quality_issue>DATWRO</annot:quality_issue><annot:error_message>Data wrong</annot:error_message>
<annot:old_value>Urszula Gacek</annot:old_value>
<owl:annotatedSource rdf:resource="http://publications.europa.eu/resource/celex/92009E000068"/><owl:annotatedTarget rdf:resource="http://publications.europa.eu/resource/authority/corporate-body/OP_DATPRO"/><
owl:annotatedProperty rdf:resource="http://publications.europa.eu/ontology/cdm#work_created_by_agent"/>
</rdf:Description>

10/07/2015: Author to be used in 22015D0921: Decision No 1/2015 of the EU-EFTA Joint Committee on Common Transit of 11 May 2015 concerning an invitation to the former Yugoslav Republic of Macedonia to accede to the Convention on a common transit procedure [2015/921]

Codes referring to EC-EFTA Joint Committee and EEC-EFTA Joint Committee were deprecated in corporate bodies table and there is no successor referring to EU-EFTA Joint Committee.

In such case, the values referring to the Joint Committee (CMT_JOIN), European Union (EURUN) and EFTA (EFTA) should be used.
If the horizontal structure of the corporate bodies will be implemented in Cellar and EUR-Lex, value EURUN will not be needed anymore in this case as it is a parent value of CMT_JOIN.

12/11/2018: Change concerning personal names – they are currently in cdm:work_created_by_agent: Personal authors would be under contributed_by (https://webgate.ec.europa.eu/CITnet/jira/browse/CDM-52).
Another change concerning contributed_by cdm:work_contributed_by_agent is removed from the notice+index and only cdm:contributed_by will be indexed&in_notice (https://webgate.ec.europa.eu/CITnet/jira/browse/CDM-119).

21/10/2019: Personal names present in cdm:work_created_by_agent for fd_013 in documents from sector 9 could be also moved to cdm:asked_by. Check https://webgate.ec.europa.eu/publications/jira/browse/CADMOS-7932

http://publications.europa.eu/resource/authority/corporate-body/COM

http://publications.europa.eu/resource/authority/corporate-body/EESC

http://publications.europa.eu/resource/authority/corporate-body/CONSIL

http://publications.europa.eu/resource/authority/corporate-body/CJ

http://publications.europa.eu/resource/authority/corporate-body/EURUN

http://publications.europa.eu/resource/authority/corporate-body/EFTA_SUC

http://publications.europa.eu/resource/authority/corporate-body/COMP

http://publications.europa.eu/resource/authority/corporate-body/EP

http://publications.europa.eu/resource/authority/corporate-body/EDPS

http://publications.europa.eu/resource/authority/corporate-body/EFTA_STC

http://publications.europa.eu/resource/authority/corporate-body/GOVREP

http://publications.europa.eu/resource/authority/corporate-body/ENER

                            
                                < cdm:work_has_resource-type rdf:resource="http://publications.europa.eu/resource/authority/resource-type/REG_IMPL"/>
                                
                            
                            

April 2015: For the time being, both properties cdm:work_has_resource-type as well as cdm:resource_legal_has_type_act_concept_type_act shall be used because of technical reasons. For the display and search purposes, only cdm:resource_legal_has_type_act_concept_type_act is currently used by the EUR-Lex.

In few months, a complete switch to cdm:work_has_resource-type will be done.

18/09/2015: Correction related to DECBES value: https://webgate.ec.europa.eu/publications/jira/i#browse/LAAION-44

http://publications.europa.eu/resource/authority/resource-type/REG_DRAFT

http://publications.europa.eu/resource/authority/resource-type/DIR_DRAFT

http://publications.europa.eu/resource/authority/resource-type/COMMUNIC_DRAFT

http://publications.europa.eu/resource/authority/resource-type/DECLAR_DRAFT

http://publications.europa.eu/resource/authority/resource-type/OPIN_EXPLOR

http://publications.europa.eu/resource/authority/resource-type/OPIN

http://publications.europa.eu/resource/authority/resource-type/OWNINI_OPIN

http://publications.europa.eu/resource/authority/resource-type/OWNINI_OPIN_ADDIT

http://publications.europa.eu/resource/authority/resource-type/STAT_REASON

http://publications.europa.eu/resource/authority/resource-type/PROP_REG

http://publications.europa.eu/resource/authority/resource-type/AMEND_PROP_REG

http://publications.europa.eu/resource/authority/resource-type/PROP_DIR

http://publications.europa.eu/resource/authority/resource-type/AMEND_PROP_DIR

http://publications.europa.eu/resource/authority/resource-type/INFO_JUDICIAL

http://publications.europa.eu/resource/authority/resource-type/ARRANG

http://publications.europa.eu/resource/authority/resource-type/NOTICE

http://publications.europa.eu/resource/authority/resource-type/ANNOUNC

http://publications.europa.eu/resource/authority/resource-type/DEC

http://publications.europa.eu/resource/authority/corporate-body/ANNOUNC

http://publications.europa.eu/resource/authority/resource-type/COMMUNIC

http://publications.europa.eu/resource/authority/resource-type/NOTIF

http://publications.europa.eu/resource/authority/resource-type/REPORT_ANNUAL

http://publications.europa.eu/resource/authority/resource-type/POSIT

http://publications.europa.eu/resource/authority/resource-type/SUM

http://publications.europa.eu/resource/authority/resource-type/RES

http://publications.europa.eu/resource/authority/resource-type/CONCL

http://publications.europa.eu/resource/authority/resource-type/STATS

http://publications.europa.eu/resource/authority/resource-type/AGREE_INTERNATION

http://publications.europa.eu/resource/authority/resource-type/AGREE_PROT

                            
                                <cdm:resource_legal_repertoire rdf:datatype="http://www.w3.org/2001/XMLSchema#string">REP</cdm:resource_legal_repertoire>
                                
                            
                            

Join practical guide (2015; ISBN 978-92-79-49121-4; ISBN 978-92-79-49084-2) – Amending acts without autonomous provisions and basic acts with amending provisions

8.3. The title of an act amending earlier acts is a special case. The title is incomplete unless it refers by number to all the acts amended. Without such a reference, it is not possible to find all the amendments to a given act. If the sole purpose of the act in question is to amend another act, either the sequential reference number and title of the act to be amended or its sequential reference number and the specific purpose of the amendment is mentioned (see points 18.9 and 18.10). In contrast, if the act in question lays down autonomous provisions and consequently amends another act in a purely subsidiary manner, only the number of that act is given (see point 19.3).

19. An act not primarily intended to amend another act may set out, at the end, amendments of other acts which are a consequence of changes which it introduces. Where the consequential amendments are substantial, a separate amending act should be adopted.

19.1. Sometimes an act with autonomous provisions alters the legal context of a given field to such an extent that other acts governing other areas within the same field need to be amended. To the extent that the amendment is only secondary to the main scope of the act, the juxtaposition of autonomous and amending provisions in the same act does not fall within the prohibition set out in Guideline 18 on the inclusion of autonomous substantive provisions in amending acts.
In order for the amendment to be apparent, it must be mentioned in the title of the act, by stating the sequential reference number of the act to be amended (see point 8.3).
Example:
Council Directive 92/96/EEC of 10 November 1992 on the coordination of laws, regulations and administrative provisions relating to direct life assurance and amending Directives 79/267/EEC and 90/619/EEC

04/11/2019: Check basic acts containing "amending" at the end of the title; many of them could be indexed with LIE

18/2/2019: Discussion with AION regarding Join practical guide, points 8.3 and 19
REP: Autonomous act containing "subsidiary" amendments (32005R0396 or 31992L0096). At the end of the title, “amending” can be found.
LIE: Amending acts containing "subsidiary" autonomous provisions, it seems to be just a theoretical example. The title of such act contains its number and document date which are directly followed by “amending”.

LIE

REP

                            
                                <cdm:resource_legal_in-force rdf:datatype="http://www.w3.org/2001/XMLSchema#boolean">true</cdm:resource_legal_in-force>
                                
                            
                            

04/11/2019: GIL-GM Acts annuled by CdJ decision - VV field - proposal to be prepared
The legal analysis methodology does not follow up on the annulments of legal acts by judgments of the Court of Justice. Currently the date of end of validity of those acts remains indefinite; therefore, they remain marked as 'in force'.

The Commission Legal Service was consulted and considered that the effect should be as if it had never existed, therefore the value contained in the date of effect field should be reproduced in the date of end of validity, and the in force indicator switched to 'not in force'. The participants agreed on this solution and indicated that the comment 'declared void by' should be shown below the title, next to the in force indicator coloured point.


This solution should also be applied to cases where the judgment annuls the decision but orders to maintain the effects of the decision in force.

11/03/2019: Display of VV on EUR-Lex - There were new values created on EUR-Lex "Not yet in force". Rules:
VV=true: "In force"
VV=false AND EV>TODAY: "Not yet in force" (expert search VV2=NOT_YET_IN_FORCE)
VV=false AND EV<TODAY: "No more in force" (expert search VV2=NO_MORE_IN_FORCE)

VV is not displayed when there is a date of notification=01/01/1001 (see: NF=01/01/1001 AND VV=false ORDER BY XC DESC)

                            
                                <cdm:resource_legal_based_on_concept_treaty rdf:resource="http://publications.europa.eu/resource/authority/treaty/TEU_2012"/>
                                
                            
                            

04/11/2019: Property cdm:resource_legal_based_on_treaty was used in the past, it has been depricated and replaced by
cdm:resource_legal_based_on_concept_treaty

                            
                                cdm:proposal_act_service_responsible rdf:datatype="http://www.w3.org/2001/XMLSchema#string">SANCO</cdm:proposal_act_service_responsible>
                                
                            
                            

04/11/2019: Check cdm properties, which are still used?

04/11/2019: Author field also contain name of responsible DG. In such cases RS just duplicates this information. Check how it is treated in IMMC.

cdm properties:
*cdm:proposal_act_service_responsible (deprecated: CDM-75 https://webgate.ec.europa.eu/publications/jira/browse/EURLEXNEW-3413)
*cdm:non-opposition_concentration_notified_service_responsible
*cdm:non-opposition_joint-venture_notified_service_responsible
*cdm:regulation_service_responsible
*cdm:decision_service_responsible
*cdm:directive_service_responsible
*cdm:document_com_other_ec_service_responsible
*cdm:act_legislative_other_oj_c_service_responsible
*cdm:act_legislative_other_oj_l_service_responsible
*cdm:staff-working-document_service_responsible
*cdm#resource_legal_service_responsible
*cdm#resource_legal_responsibility_of_agent

ENER

                            
                                <cdm:resource_legal_information_miscellaneous rdf:datatype="http://www.w3.org/2001/XMLSchema#string">JOIN 2014/0034</cdm:resource_legal_information_miscellaneous>
                                
                            
                            

Judgment of the Court of 14 December 2000 Parfums Christian Dior SA v TUK Consultancy BV and Assco Gerüste GmbH and Rob van Dijk v Wilhelm Layher GmbH & Co. KG and Layher BV.
References for a preliminary ruling: Arrondissementsrechtbank 's-Gravenhage and Hoge Raad der Nederlanden - Netherlands.
Agreement establishing the World Trade Organisation - TRIPs Agreement - Article 177 of the EC Treaty (now Article 234 EC) - Jurisdiction of the Court of Justice - Article 50 of the TRIPs Agreement - Provisional measures - Interpretation - Direct effect.
Joined Cases C-300/98 and C-392/98
European Court Reports 2000 Page I-11307

Additional information:
Joined case : 698J0392

Council Regulation (EC) No 198/2001 of 29 January 2001 amending the Annex to Regulation (EC) No 2042/2000 imposing a definitive anti-dumping duty on imports of television camera systems originating in Japan

Additional information:
Dumping

Partnership agreement between the members of the African, Caribbean and Pacific Group of States of the one part, and the European Community and its Member States, of the other part, signed in Cotonou on 23 June 2000

Additional information:
Validity: notice of termination of 6 months

Commission Decision of 15/12/2000 declaring a concentration to be compatible with the common market (Case No IV/M.2245 - METSÄ-SERLA / ZANDERS) according to Council Regulation (EEC) No 4064/89 (Only the English text is authentic)

Additional information:
NACE=DE.21.00

Amendment by France of public service obligations in respect of scheduled air services within France (Text with EEA relevance)

Additional information:
EEA relevance

2000/770/EC: Internal Agreement between Representatives of the Governments of the Member States, meeting within the Council, on the Financing and Administration of Community Aid under the Financial Protocol to the Partnership Agreement between the African, Caribbean and Pacific States and the European Community and its Member States signed in Cotonou (Benin) on 23 June 2000 and the allocation of financial assistance for the Overseas Countries and Territories to which Part Four of the EC Treaty applies

Additional information:
Validity: until adoption of definitive measures

                            
                                <cdm:proposal_act_service_associated rdf:datatype="http://www.w3.org/2001/XMLSchema#string">MARKT</cdm:proposal_act_service_associated>
                                
                            
                            

04/11/2019: Check cdm properties, which are still used?

cdm properties:
*cdm:proposal_act_service_associated (deprecated: CDM-75 https://webgate.ec.europa.eu/publications/jira/browse/EURLEXNEW-3413)
*cdm:regulation_service_associated
*cdm:directive_service_associated
*cdm:decision_service_associated
*cdm:document_com_other_ec_service_associated
*cdm:staff-working-document_service_associated
*cdm#resource_legal_service_associated

                            
                                <cdm:resource_legal_position_eesc rdf:datatype="http://www.w3.org/2001/XMLSchema#string">AVIS-SECTION 2013/4522 FIN</cdm:resource_legal_position_eesc>
                                
                            
                            

04/11/2019: Check how this field is used and whether it is needed or not. Check also IMMC.

http://publications.europa.eu/ontology/cdm#act_preparatory

http://publications.europa.eu/ontology/cdm#opinion_other_committee_ecsc

http://publications.europa.eu/ontology/cdm#opinion_consultation_eesc

http://publications.europa.eu/ontology/cdm#position_council

http://publications.europa.eu/ontology/cdm#proposal_regulation_ec

http://publications.europa.eu/ontology/cdm#proposal_directive_ec

http://publications.europa.eu/ontology/cdm#info_decision_cjeu

http://publications.europa.eu/ontology/cdm#agreement_international

http://publications.europa.eu/ontology/cdm#resource_legal

http://publications.europa.eu/ontology/cdm#legislation_secondary

http://publications.europa.eu/ontology/cdm#act_surveillance-authority_efta

http://publications.europa.eu/ontology/cdm#document_budget_ep

http://publications.europa.eu/ontology/cdm#work

http://publications.europa.eu/ontology/cdm#opinion

                            
                                <cdm:treaty_stored_by_agent rdf:resource="http://publications.europa.eu/resource/authority/fd_040/I-G"/>
                                
                            
                            

04/11/2019: Check cdm properties

04/11/2019: cdm properties:
*cdm:treaty_stored_by_agent
*cdm:legislation_complementary_stored_by_agent
*cdm:agreement_international_stored_by_agent

                            
                                <cdm:resource_legal_comment_internal rdf:datatype="http://www.w3.org/2001/XMLSchema#string">MAN2</cdm:resource_legal_comment_internal>
                                
                            
                            

04/11/2019: Check wheather this field and values MAN are still useful or not.

28/02/2017: New value for ephemeral documents introduced (EPH).

                            
                                <cdm:opinion_eesc_number_session rdf:datatype="http://www.w3.org/2001/XMLSchema#string">{SESSION|http://publications.europa.eu/resource/authority/fd_345/SESSION} 376</cdm:opinion_eesc_number_session>
                                
                            
                            

12/12/2018: Changes in cdm proerties EURLEXNEW-3672 The following cdm properies shall be depricated:
*cdm:opinion_eesc_number_session
*cdm:act_other_cor_number_session
*cdm:act_other_eesc_number_session
*cdm:opinion_consultation_cor_number_session
*cdm:opinion_consultation_eesc_number_session
*cdm:opinion_other_cor_number_session
*cdm:opinion_other_eesc_number_session
*cdm:question_parliamentary_number_session

                            
                                <cdm:resource_legal_addresses_institution rdf:resource="http://publications.europa.eu/resource/authority/fd_050/CONS"/>
                                
                            
                            

(13/07/2015): New code <LIBELLE CODE="CH">Switzerland</LIBELLE> was created in FD_050. Should be used also in this document: 32015D1056

(03/05/2016): Metadata field Addressee should not cover cases like Communications to the European Parliament and the Council or EP resolutions (to be forwarded to the Council, Commission and national parliaments).

(03/05/2016): CDM-135: In the context of merger cases, the Commission decisions declaring a concentration to be compatible with the common market concern two or more parties (usually companies). See an example https://eur-lex.europa.eu/legal-content/EN/ALL/?uri=CELEX:32017M8399 However, such values are currently stored as ‘Addressee’ (cdm:resource_legal_addresses_organization ) but this is not correct because these companies are only the object of the Commission investigation, and not the addressee of the decision. Therefore, it is necessary to create a new property which would store the names of these companies. Once this is created, the CELLAR team will have to move all the values from 'Addressee' into the new property.
The label for the new property should be : 'Companies involved".
The following new cdm property is going to be replaced (in_notice + to_be_indexed): cdm:resource_legal_involves_agent

04/11/2019: COUNTRY – see https://webgate.ec.europa.eu/publications/jira/browse/EURLEXNEW-3599, to be used for cdm:resource_legal_addresses_organization
cdm:resource_legal_addresses_country refers to the country being the addressee of an act while annotation COUNTRY refers to the "domicile" of the company being the addressee of an act…

04/11/2019: In EURLEXNEW-3713 AD should be linked to cdm#resource_legal_addresses_agent (proposed xpath */NOTICE/WORK/RESOURCE_LEGAL_ADDRESSES_AGENT/*)
when this will be done, more specific cdm#resource_legal_addresses_institution/organization/country could be removed from index+notice
The current ontology:
cdm:addresses
- cdm:resource_legal_addresses_agent (in_notice, to_be_indexed)
- - cdm:resource_legal_addresses_institution (in_notice, to_be_indexed)
- - cdm:resource_legal_addresses_organization (in_notice, to_be_indexed)
- - cdm:resource_legal_addresses_country (in_notice, to_be_indexed)

04/11/2019: Check cdm properties and pending changes:
*cdm:resource_legal_addresses_institution
*cdm:resource_legal_addresses_organization
*cdm:resource_legal_addresses_agent
*cdm:resource_legal_addresses_country

                            
                                <j.0:work_part_of_dossier rdf:resource="http://publications.europa.eu/resource/procedure/2015_288"/>
                                
                            
                            

                            
                                <cdm:agreement_international_has_type_comment_concept_type_comment rdf:resource="http://publications.europa.eu/resource/authority/fd_301/ACC%2FMIXTE"/>
                                
                            
                            

04/11/2019: Check how this field is used and whether it is needed or not. Check also IMMC.

                            
                                <cdm:resolution_legislative_ep_reported_by_person rdf:resource="http://publications.europa.eu/resource/authority/fd_013/CAPOULAS_SANTOS"/>
                                
                            
                            

04/11/2019: cdm properties
*cdm:resolution_legislative_ep_reported_by_person
*cdm:document_budget_ep_reported_by_person
*cdm:resolution_legislative_ep_reported_by_person
*cdm:resolution_other_ep_reported_by_person
*cdm:decision_internal_ep_reported_by_person
*cdm:act_other_ep_reported_by_person
*cdm:opinion_consultation_eesc_reported_by_person
*cdm:opinion_other_eesc_reported_by_person
*cdm:opinion_eesc_reported_by_person
*cdm:act_other_eesc_reported_by_person
*cdm:opinion_consultation_cor_reported_by_person
*cdm:opinion_other_cor_reported_by_person
*cdm:act_other_cor_reported_by_person

04/11/2019: check cdm properties

                            
                                <cdm:resource_legal_uses_originally_language rdf:resource="http://publications.europa.eu/resource/authority/language/SPA"/>
                                
                            
                            

                            
                                <cdm:question_parliamentary_asked_by_group_parliamentary rdf:resource="http://publications.europa.eu/resource/authority/fd_290/FRACTIO-09%2F004"/>
                                
                            
                            

                            
                                <cdm:question_parliamentary_term_parliamentary rdf:datatype="http://www.w3.org/2001/XMLSchema#string">7</cdm:question_parliamentary_term_parliamentary>
                                
                            
                            

04/11/2019: Check the values used in this field
FD_285
n.a. (#string) However, only codes are exposed (not decoded), so 01, 02, etc.

30/11/2015: A new concept for the 8th parliamentary term was created in FD_285 (L-08 Eighth legislature) and published in MDR publication 20151118-0 (release date: 18/11/2015). Provisional value OP_DATPRO should be removed and replaced by L-08.

                            
                                <j.0:communication_cjeu_defended_by_agent rdf:resource="http://publications.europa.eu/resource/authority/fd_110/IC"/>
                                
                            
                            

                            
                                <j.0:communication_cjeu_requested_by_agent rdf:resource="http://publications.europa.eu/resource/authority/fd_110/PART"/>
                                
                            
                            

                            
                                <j.0:communication_cjeu_has_type_procedure_concept_type_procedure rdf:resource="http://publications.europa.eu/resource/authority/fd_100/ANNU"/>
                                
                            
                            

                            
                                22016A0311(01)
22012A0413(01)
22014A0611(02)
22014A0412(01)
                                
 
                            
                                Arrangement between the European Union and the Swiss Confederation on the modalities of its participation in the European Asylum Support Office
                                
 
                            
                                ARRANGEMENT entre l'Union européenne et la Confédération suisse sur les modalités de sa participation au bureau européen d'appui en matière d'asile
                                
                            
                            

arrangement between EU and third country

DTS_SUBDOM = INTER_AGREE AND (TI~arrangement between) ORDER BY XC DESC

                            
                                22016A0420(01)
22016A0421(01)
22014A0712(01)
                                
 
                            
                                Participation Agreement between the European Union and the Swiss Confederation on the participation of the Swiss Confederation in the European Union Advisory Mission for Civilian Security Sector Reform in Ukraine (EUAM Ukraine)
                                
 
                            
                                ACCORD DE PARTICIPATION
entre l'Union européenne et la Confédération suisse relatif à la participation de la Confédération suisse à la mission de conseil de l'Union européenne sur la réforme du secteur de la sécurité civile en Ukraine (EUAM UKRAINE)
                                
                            
                            

Usually between EU and Swiss concerning CFSP

TI~"participation agreement" AND DTS_SUBDOM = INTER_AGREE ORDER BY XC DESC

                            
                                22016A0521(01)
22019A0508(01)
22019A0426(01)
                                
 
                            
                                Protocol amending the Euro-Mediterranean Aviation Agreement between the European Union and its Member States, of the one part, and the Hashemite Kingdom of Jordan, of the other part, to take account of the accession to the European Union of the Republic of Croatia
                                
 
                            
                                PROTOCOLE
modifiant l'accord euro-méditerranéen relatif aux services aériens entre l'Union européenne et ses États membres, d'une part, et le Royaume hachémite de Jordanie, d'autre part, pour tenir compte de l'adhésion à l'Union européenne de la République de Croatie
                                
                            
                            

Usually amendments to an international agreement (link - amendment)

(TI~Protocol amending) AND DTS_SUBDOM = INTER_AGREE AND DTT=A ORDER BY XC DESC